Release

Purpose of the Document.

We are releasing this policy to build trust between Eyedid(SeeSo) users and developers, and to explain what each version means.

---

Version

Eyedid(SeeSo) SDK is using Semantic versioning.

It has a structure of Major.Minor.Patch.

Basic rules

1. The number in each version is a natural number with no leading zeros.
2. The version should always be incremented.
3. After distributing a package with a specific version, the contents of that version should never be changed. If there are any changes, be sure to distribute them in a new version.
4. When the major version is changed, Minor and Patch are initialized to 0.
5. When the minor version is changed, the Patch is initialized to 0.

Major.

1. Changes made are not backward compatible.
2. A big change occurred.

Minor.

1. New functions are added while backward compatible.
2. API with new functions is released, but the existing public API is backward compatible.
3. An existing function is modified, or method usage is altered.

Patch.

1. Bug fixes.
2. SDK's code is internally modified.

Beta.

1. Beta versions are created when major or minor updates are required.
2. The call structure can be freely changed.
3. It may not work properly.
4. When the beta version is thoroughly tested, the beta version is changed to the full version, and the major or minor version is increased.

---

Release.

About Release

1. The current release is on SeeSo Manage.
2. For each platform, the minor version is unified and released.
3. In the future, we plan to support the use of SDK management tools used by each relevant platform.
4. In order to increase the reliability of the SDK, our Eyedid(SeeSo) team decided to publish a safe version and a beta version in the form of providing only the latest SDK.

Release rules.

1. Beta version will be released before any new update (major or minor).
2. We will always release the using Android and Desktop(C++) as a beta version first.
3. After the release of beta versions of Android and Desktop(C++), other platforms will also release beta versions as soon as possible.
4. When it is determined that stability is secured, we will support the official release.
5. Even after the official release, even if a hotfix occurs, we will continue to update the patch version.

Beta Versioning Rule

Beta releases are denoted by adding "beta(beta version number)" after the upcoming release number. For example, if the current release version is 3.0.1, and a developer wishes to preview the next minor release, the release would be 3.1-beta1.